Communication system control method

ABSTRACT

A method of controlling the operation of a communication system is described, where the system comprises a first entity  2  for sending a first data object  21  to a terminal device  4  and a second entity  3  for sending a second data object to the terminal device at the request  41  of the terminal device  4 . The communication system also comprises a data transfer entity  11  and a charging entity  5 . The data transfer entity  11  records charging relevant parameters related to the transfer of the first data object. It is proposed that the second entity  3  is controlled to output a predetermined triggering message to the data transfer entity  11  and/or the charging entity  5 , where the operation of processing the charging relevant parameters in a charging procedure is postponed until the predetermined message is received.

FIELD OF THE INVENTION

The present application relates to a method of controlling the operationof a communication system, to methods of controlling individual entitiesin such a communication system, and to the individual entities in thecommunication system. More specifically, the present application dealswith improved ways of controlling an overall charging operation in acommunication system, to thereby allow a more flexible charging andbilling of services.

BACKGROUND OF THE INVENTION

In the field of telephone communications, a well-known charging conceptconsists in recording one or more parameters related to the transfer ofinformation to a terminal and then performing charging and billing onthe basis of such recorded parameters. For example, in standardtelephone systems the amount of time for a call communication isrecorded as a basis for billing this call communication. Another exampleof a parameter related to the transfer of information to a terminaldevice is the amount or volume of transferred data.

In a communication network, such as a telephone network, an entity forhandling communications to and from a terminal device can record theabove-mentioned parameters and appropriately forward these parameters toa charging entity that handles the charging and billing of services tousers of terminal devices.

The term “entity” as used in the present specification and claims refersto a functional element assigned to provide a certain function in acommunication system. An entity can therefore be provided by hardware,software or any suitable combination of hardware and software. An entitycan be provided at one physical location, e.g. be provided by softwarerunning on a given server, or can be spread out over several physicallocations, e.g. can be provided by software running in a distributedarchitecture.

Recently, a concept for distributing information to users has beenproposed, which is called Digital Rights Management (DRM). In DRMcontent is not simply passed to a user of a terminal device, but muchrather two data objects are generated, a first data object known as acontent object and a second data object know as a rights object. Thecontent objects are handled by a distribution entity and the rightsobjects are handled by a rights entity, which entities can be providedby two respective servers, or also by a single server. The basic idea ofDRM is that the content in the content object is not readily accessibleto the user of the terminal device, and that the rights object isnecessary for gaining access to the content. Therefore, after havingreceived the content object, a user will request from the rights entitya rights object associated with the down-loaded content object, in orderto be able to access the content of the content object.

The content object can be of any desired nature, e.g. containing audioinformation (such as a music file), or a combination of audio and videoinformation (such as a video clip) or can be data of other nature (suchas a text or a computer game). The rights object can also have anydesired nature, e.g. provide one-time access to the content object, orunrestricted access. As an example, the content in the content objectcan be encrypted, and the rights object comprises information fordecrypting said content.

OBJECT OF THE INVENTION

It is the object of the present invention to provide improved controlmethods and associated entities for communication systems in which firstand second data objects are provided to a terminal device, said firstand second data units being associated in a predetermined way, in viewof making the charging and billing operation more flexible.

SUMMARY OF THE INVENTION

The object is solved by the basic methods of claim 1 and claim 6 and bythe methods and devices described in the other independent claims.Advantageous embodiments are described in the dependent claims.

The invention relates to the control of a communication system thatcomprises a first entity for sending a first data object to a terminaldevice, a second entity for sending a second data object to the terminaldevice, said second data object having a predetermined association withthe first data object, a data transfer entity for transferring data tothe terminal device and recording one or more charging relevantparameters associated with the transfer of data to the terminal device,where the data transfer entity is arranged to transfer the first dataobject to the terminal device, and the data transfer entity is part of acommunication network, and a charging entity for collecting andprocessing charging information related to the providing ofcommunication services by the communication network, where the datatransfer entity is arranged for providing recorded charging relevantparameters to the charging entity.

In this communication system, the first and second entity may or may notbe part of the mentioned communication network, and equally the chargingentity may or may not be a part of this communication network. As anexample, the communication network can be a telephone network, such as amobile telephone network or a fixed line telephone network. As aconsequence, the data transfer entity can be any entity in the networkthat handles the transfer of data, such as a node in a telephonenetwork.

The first entity may send the first data object at the request of theterminal device or at the request of some other entity, e.g. in anetwork push situation. Equally, the second entity may send the seconddata object to the terminal device at the request of the terminaldevice, or at the request of some other entity.

Preferably, the first data object comprises data to be accessed by auser of the terminal device, and the second data object comprisesinformation for enabling access to the data of the first data object,e.g. the first data object can be a content object and the second dataobject can be a rights object. However, it is to be noted that thepresent invention is by no means restricted to this example and can beapplied to any system in which a first and second data object are sentto a terminal device, said first and second data object being associatedin a predetermined way.

The correlation between the first and second data object can be providedin any suitable or desirable way, e.g. with the help of a knownidentifying scheme such as URI (Universal Resource Indicator) or anysimilar scheme.

In accordance with the present invention, the first entity is controlledto send the first data object to the terminal device, and the datatransfer entity is controlled to record one or more charging relevantparameters related to the transfer of the first data object to theterminal device. The one or more charging relevant parameters can beselected in any suitable or desirable way, and can e.g. be the amount orvolume of data transferred with the first data object and/or the amountof time necessary for transferring the first data object.

According to a first aspect of the invention, the second entity iscontrolled in such a way that after having received a request forsending the second data object to the terminal device, the second entityoutputs a predetermined message to the data transfer entity, and thedata transfer entity is controlled to make the providing of the one ormore recorded charging relevant parameters that relate to the transferof the first data object dependent on the receipt of the predeterminedmessage.

In other words, the forwarding of the charging relevant parametersrecorded by the data transfer entity to the charging entity depends onreceiving the predetermined message.

According to a second aspect, the second entity is controlled in such away that after having received the request for sending the second dataobject to the terminal device, the second entity outputs a predeterminedmessage to the charging entity, and the charging entity is controlled insuch a way as to make the processing of the one or more chargingrelevant parameters related to the transfer of the first data object(said charging relevant parameters having been forwarded by the datatransfer entity) dependent on the receipt of the predetermined message.

In other words, the processing of the charging relevant parameters forthereby performing a charging or billing operating on the basis of thesecharging relevant parameters is made dependent on the receipt of thepredetermined message from the second entity.

The common concept of the present invention is thereby that the processof charging or billing on the basis of the parameters recorded for thetransfer of the first data object is made dependent on a request forsending the second data object to the terminal device, e.g. a user ofthe terminal device requesting the second data object.

This basic concept of the invention provides one advantage in that it ispossible to avoid charging or billing of the transfer of the first dataobject if sending of the second data object is never requested. Thisgreatly increases the flexibility for the charging and billingoperation. Namely, taking DRM as described in the introduction as anexample, it is well possible that an end user has down-loaded a contentobject, or has received the content object via a so-called network-push(i.e. he has not requested the content object but has received it at theinitiative of the network operator, e.g. in a course of an advertisingcampaign), but does not wish to retrieve the rights object. This can bedue to a number of reasons, e.g. the user is not interested in thecontent, the content is outdated, the user has looked at a preview andis not interested in the rest of the content, the user is not willing topay a fee that is levied for retrieving the rights object, the user hasalready received the same content before, etc. In such cases, the userwill probably delete the content object without making use of it, i.e.without retrieving (and possibly paying) for the rights object. Inaccordance with the present invention, it is now possible that thecharging and billing operation in such a case can be adapted to thissituation, namely that no charging or billing is conducted if theend-user who received the first data object is not interested, i.e. doesnot retrieve the second data object.

Another advantage is that it is possible to make the rate applied tocharging of the transfer of the first data object dependent on the timeof requesting the sending of the second data object.

It may be noted that the possible debtor of services for transferringthe first data object can be the end-user, but can also be a differentparty, e.g. a party that initiates a network-push operation, such as anadvertiser. In any case, with the present invention it is possible tomake the charging or billing operation with respect to the debtor moreflexible. It is noted that the invention can be applied to any type ofcharging or billing operation, e.g. postpaid systems, prepaid systems orcombinations of post- and prepaid systems.

BRIEF DESCRIPTION OF DRAWINGS

The present invention will now be described in more detail with respectto preferred embodiments, by making reference to the figures, in which

FIG. 1 shows a schematic representation of a communication network towhich the present invention can be applied in one aspect,

FIG. 2 shows a schematic representation of a communication system towhich the present invention can be applied in another aspect,

FIG. 3 shows a schematic representation of signalling associated with anembodiment of the invention,

FIG. 4 shows a schematic representation of signalling associated withanother embodiment of the invention,

FIG. 5 shows a schematic representation of signalling associated with aanother embodiment of the invention,

FIG. 6 shows a schematic representation of signalling associated withanother embodiment of the invention, and

FIG. 7 shows a schematic representation of signalling associated withyet another embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS

Although the following description of embodiments of the invention willmake reference to specific examples of data objects, communicationnetworks and corresponding entities, these examples only serve toprovide a more comprehensive understanding and are not intended to belimiting.

FIG. 1 shows a schematic representation of a communication system towhich the present invention can be applied. Reference numeral 2represents a first entity for sending a first data object to a terminaldevice 4. For example, entity 2 can be a distribution server in a DRMsystem, for outputting content objects. The terminal device 4 isarranged to communicate with a network 10, where the communication toand from terminal device 4 is handled by a data transfer entity 11. Forexample, the network 10 can be a mobile telephone network, e.g.operating in accordance with GSM (Global System for Mobilecommunication), GPRS (General Packet Radio Service), UMTS (UniversalMobile Telephone System) or any other mobile telephone standard. TakingGPRS as an example, the data transfer entity can be a Gateway GPRSSupport Node (GGSN) or a Serving GPRS Support Node (SGSN). If a network10 is a mobile telephone network, then terminal device 4 is a mobilestation. The communication network 10 can, however, also be some otherform of telephone networks, e.g. a PSTN or a ISDN, in which case theterminal device 4 is an appropriate terminal for the given telephonenetwork. The communication network 10 can also be a general datacommunication network, e.g. a network based upon the Internet protocol(IP), in which case the terminal device 4 is again an appropriatematching terminal, such as a personal computer (PC) attached to the IPbased network.

The representation of communication network 10 is only schematic and forsimplicity only one data transfer entity 11 is shown. As is well knownto the skilled person, the communication network will generally comprisea plurality of data transfer entities for accomplishing communicationwithin the network and to a variety of terminal devices communicatingwith the network.

FIG. 1 furthermore shows a second entity 3 for sending a second dataobject to the terminal device 4, at the request of said terminal device4 or some other entity, where the second data object has a predeterminedassociation with the first data object. For example, the second entity 3can be a rights server in a DRM system.

The first and second entity 2, 3 are shown as being outside of network10. However, it may be noted that they can also be part of network 10.FIG. 1 furthermore shows an entity 6 that provides the first and seconddata object to the first and second entity, respectively. In the contextof DRM the entity 6 could be a so-called packager, i.e. an entity thatreceives content information from an appropriate content server andgenerates a content object and a rights object on the basis thereof.However, the present invention is not restricted to any specific mode ofgenerating the first and second data objects, and it is e.g. alsopossible that the first and second data object are generated at thefirst or second entity and then provided to the respectively otherentity.

FIG. 1 furthermore shows a charging entity 5 which is arranged tocollect and process charging information related to the providing ofcommunication services by the communication network 10. The chargingentity 5 is shown as being outside of network 10, but could equally wellbe a part of network 10.

In the communication system thus formed, the data transfer entity 11 isarranged to record one or more charging relevant parameters associatedwith the transfer of data to the terminal device 4. A dotted linebetween the charging entity 5 and the data transmit entity 11 representsthat the data transfer entity 11 is arranged to provide recordedcharging relevant parameters to the charging entity 5. The chargingentity 5 is arranged to run charging/billing procedures, in accordancewith which the charging relevant parameters are processed in order togenerate bills or charging statements for users of the network 10.

In FIG. 1, arrows 21 represent the sending of the first data object tothe terminal device 4. It is noted that the passing of the data objectfrom the first entity 2 to the data transfer entity 11 may involve aplurality of further data transfer entities in the network 10, which arenot shown for simplicity. Any data transfer entity along the pathbetween the first entity 2 and the terminal device can be used as thedata entity 11 shown in FIG. 1. For example, data transfer entity 11 canbe a gateway entity that provides access to network 10 for the firstentity 2, or it can be the final serving entity that provides service tothe terminal device 4.

The data transfer entity 11 of FIG. 1 records one or more chargingrelevant parameters (such as the down-load time and/or the amount orvolume of the first data object) related to the transfer of the firstobject to terminal device 4. Arrows 41 represent the request sent by theterminal device 4 to the second entity 3, for sending the second dataobject to the terminal device 4. For simplicity, it is shown thatmessage 41 passes by data transfer entity 11, but it is noted that thisrequest for the second data object could be sent via any suitable pathbetween terminal device 4 and second entity 3, either through network 10or over some other communication path.

In accordance with the example of FIG. 1, the data transfer entity 11 isfurthermore controlled in such a way that it makes the providing of theone or more recorded charging relevant parameters associated with thefirst data object dependent on the receipt of a predetermined message 31from the second entity 3, where the second entity 3 only outputs saidmessage 31 after having received the request 41 for sending the seconddata object. In other words, the process of performing a charging andbilling operation on the basis of the one or more recorded chargingrelevant parameters is postponed until message 31 is sent from thesecond entity 3 to the data transfer entity 11. In this way, if the userof terminal device 4 and no other entity ever requests the second dataobject, then it is possible to prevent that costs are charged or billedon the basis of the charging relevant parameters recorded for thetransfer of the first data object. Additionally, if the sending of thesecond data object is requested, it is possible to make the chargingdependent on the point in time of said request.

FIG. 2 shows a communication system that is very similar to that of FIG.1, and where the same units, entities and messages bear the samereference numerals as in FIG. 1, such that a repeated description is notnecessary. As can be seen, in the system of FIG. 2, the first entity 2sends the first data object to terminal device 4 in a message 21, andthe terminal device 4 requests the sending of the second data objectwith a message 41. In contrast to the example of FIG. 1, the secondentity 3 is controlled to output a predetermined message 32 to thecharging entity 5 subsequent to receiving the request 41, and thecharging entity 5 is controlled to make the processing of the one ormore charging relevant parameters related to the transfer of the firstdata object dependent on the receipt of said message 32. Thepredetermined message 32 is shown as being transmitted through network10 from the second entity 3 to the charging entity 5. It is noted thatit could also be transported over any other suitable communication pathin or outside of network 10.

The effect of the example in FIG. 2 is the same as in the example ofFIG. 1, namely that a charging or billing on the basis of the one ormore charging relevant parameters recorded for the transfer of the firstdata object is dependent on the second entity receiving a request forthe second data object.

It may be noted that the concepts of FIGS. 1 and 2 can be combined, i.e.that upon receiving the request 41 for sending the second data object,the second entity 3 can output a message 31 to data transfer entity 11and a message 32 to charging entity 5, each message 31, 32 informing therespective destination entity that a previously postponed billingoperation based on the recorded charging relevant parameters for thefirst data object can be enabled.

The charging relevant parameters recorded by the data transfer entity 11can be such that one or more of said parameters is communicated from thefirst entity 2 to the data transfer entity 11. For example, the amountor volume of data sent with the first data object is known to the firstentity 2 and can directly be communicated to the data transfer entity11. Equally, the data transfer entity 11 can be arranged to measure oneor more charging relevant parameters while transferring the first dataobject, e.g. the amount of time necessary for conducting the transfer.Naturally, the data transfer entity 11 can also measure the amount orvolume of data associated with the first data object.

Preferably, the second entity 3 in the examples of both FIGS. 1 and 2 isarranged to run a clean-up procedure in the course of which it ispossible to delete second data objects. For example, the second entity 3can be arranged to perform such a clean-up procedure on the basis of apredetermined time period since storing a given second data object. Inother words, if no request for sending a second data object is receivedwithin a predetermined time since storing the object, it is deleted.Other clean-up mechanisms are possible, e.g. each second data object mayhave an expiration date set within itself, said expiration dateindicating when to delete said second data object. In accordance withthis preferred implementation of the second entity that has the clean-upfeature, the second entity sends a notification message that informs ofthe deleting of the second data object to one or both of the datatransfer entity 11 and the charging entity 5. The data transfer entity11 and/or the charging entity 5 are then arranged to delete the one ormore charging relevant parameters related to the transfer of the firstdata object that is associated with the deleted second data object, inresponse to receiving this notification message.

Now various examples of implementing the basic concepts described abovein connection with FIGS. 1 and 2 shall be described on the basis ofFIGS. 3 to 7. For simplicity, the request for sending the second dataobject to the terminal device is always shown as originating at theterminal device. This is in fact a preferred implementation, as the userof the terminal device thereby has a measure of control. However, it isequally possible that the request for sending the second data object tothe terminal device is output by some other entity in or outside of thecommunication network, e.g. by an advertiser performing a network-pushoperation.

FIG. 3 shows a schematic example of signals exchanged between entitiesoperating according to the concept explained in connection with FIG. 1.Each vertical line relates to an entity indicated at the top, where thereference numerals for the entities are the same as used in FIG. 1.

Initially, the source 6 of the first and second data object sends thefirst data object to the first entity in message 302, and the seconddata object to a second entity 3 in message 301.

The first entity 2 can be arranged to determine whether the first dataobject is to be treated in such a way that the charging of the transferis to be postponed until the second data object associated with thefirst data object is requested and retrieved. This decision can beconducted in any suitable or desirable way, e.g. on the basis of thetype of data (or type of content) in the first data object, on the basisof the provider of said first data object, on the basis of the end-user(terminal 4), or any combination of these criteria. It may also be notedthat the indication that the charging of transfer related parameters forthe given first data unit is to be postponed, can also be given from thesource 6 to the first entity 2 as a part of message 302, in which casethe first entity 2 does not itself have to conduct any decisionprocedure.

With message 303, the first entity 2 informs the terminal device 4 thatcharging on the basis of parameters related to the transfer of the firstdata object is to be postponed until the second data object isrequested. In response thereto, the terminal device 4 sends a controlmessage to the data transfer entity 11, said control message containingcontrol information for postponing the providing of the one or morecharging relevant parameters until the receipt of a predeterminedmessage from the second entity 3. This control message 304 may be arequest message or a command message. In the request message, the datatransfer entity 11 is asked to postpone the forwarding and the datatransfer entity 11 may grant or refuse the request, whereas if thecontrol message is a command message, then the data transfer entity 11has no choice but to follow the command. In the event that the datatransfer entity 11 has a decision to make, it is possible that thisdecision can also be conducted by another entity in or outside of thenetwork, which possibility is not shown in FIG. 3 for the purpose ofsimplicity.

The data transfer entity 11 responds to the control message 304 bysending a message 305, which can be a granting or refusing of therequest if message 304 was a request, or a simple acknowledgement ofreceiving a command if message 304 was a command. The terminal device 4can optionally notify the user of the device of the information receivedin message 305, by any suitable or desirable means, e.g. via a displayprovided on terminal device 4.

In response to receiving message 305, the terminal device 4 forwards thereceived answer to first entity 2 in message 306. The first entity 2 canthen inform the second entity 3 of this with message 307. It may benoted that message 306 may also contain addressing informationidentifying the address of data transfer entity 11, where this addressinformation is also passed on to second entity 3 in message 307.

It is observed that as an alternative to messages 303 to 307, it is alsopossible that the first entity 2 first queries the terminal device 4about the address of data transfer entity 11, and after having receivedthis address, sending the control message containing a request orcommand directly to the data transfer entity 11.

It is also noted that the first and second entities 2, 3 can obtain theaddressing information for terminal device 4 in any suitable ordesirable way. For example, the address of terminal device 4 can beprovided together with the first and second data object, or the source 6for first and second data objects can provide appropriate lists ofterminal device addresses of all terminal devices to which first dataobjects are to be provided.

Returning to the example of FIG. 3, arrow 308 represents transferringthe first data object from first entity 2 to terminal device 4. Thistransfer is conducted via data transfer entity 11, which records one ormore charging relevant parameters associated with said transfer of thefirst data object. As already specified, the parameter values can begained by measuring the data transfer and/or by receiving the parametervalues from the first entity 2.

In the example of FIG. 3, it is assumed that the user of terminal device4 eventually decides to obtain the second data object associated withthe first data object, and consequently a message 309 requesting saidsecond data object is sent from the terminal device 4 to the secondentity 3. The terminal device 4 can obtain the address of second entity3 in any suitable or desirable way, where it is generally preferable toprovide this address to the terminal device 4 as a part of message 308,i.e. together with the first data object.

In response to receiving the request in message 309, the second entity 3sends a triggering message 310 to data transfer entity 11. Thistriggering message 310 is the predetermined message that lets datatransfer entity 11 forward the one or more charging relevant parametersassociated with the transfer of the first data object to the chargingentity 5, see message 311. The charging entity 5 can then conduct acharging and billing operation on the basis of these parameters as issuitable or desirable.

In principle, the second entity 3 can directly respond to the request309 by sending the second data object in a message 314. However, in theexample of FIG. 3 an option is included according to which the secondentity 3 first sends a message 312 to the charging entity 5, saidmessage 312 containing information on the second data object requestedby the user of terminal device 4. For example, it is possible that thereare a variety of second data objects, where the selection of a givendata object can be conducted automatically on the basis of the type ofthe first data object, and/or based on a selection made by the user ofterminal device 4 with message 309. For example, if the first object isa content object and the content object is a piece of music, then therecan be the option of the second data object being a first type of rightsobject (e.g. for listening to the piece of music once) or a second typeof rights objects (e.g. for listening to the piece of music a givennumber of times or an indeterminate number of times), where the costs ofthe first type of right are different from the costs of the second typeof rights, but the billing operation associated with down-loading thesecond data object is also handled by the charging entity 5.

In response to receiving message 312, charging entity 5 makes a decisionon whether the second entity 3 should indeed provide the requestedsecond data object (e.g. on the basis of the funds assigned to therequesting user), such that the second entity 3 will only send thesecond data object 314 in response to an acknowledgement message 313from charging entity 5, in which the sending of the second data objectis given an OK.

In other words, the option indicated by messages 312, 313 consists incontrolling the second entity 3 to send the information message 312 tocharging entity 5, where the information message 312 comprisesinformation associated with the second data object, and controlling thesecond entity 3 to make the sending of the second data object dependenton receiving an enable message 313 from the charging entity 5. Thecharging entity 5 is controlled to conduct an enable message outputprocedure in response to receiving the information message 312,comprising a decision step of whether or not to output the enablemessage 313. The decision step depends on the information contained ininformation message 312, and possibly also on other information, e.g.the above-mentioned fund information related to a particular userrequesting a particular second data object.

As already remarked above, several variations of the example of FIG. 3are possible, and it should also be remarked that the sequence of manymessages can be changed without changing the accomplished effect. Also,the operations started by first entity 2 with messages 303 and 306 canalso be performed by the second entity 3.

FIG. 4 shows another embodiment of the invention. Initially, the sourceof the first and second data object 6 sends the first and second dataobjects to the first and second entities 2, 3, see messages 401 and 402.Messages 401 and 402 are identical to messages 301, 302 shown in FIG. 3,such that a renewed description is not necessary. In the embodiment ofFIG. 4, the first entity 2 immediately sends the first data object toterminal device 4 in a message 403. In the embodiment of FIG. 4, thedata transfer entity 11 is arranged to perform an analysis of the firstdata object during its transfer, which is symbolized by circle 404 inFIG. 4. Depending on the result of the analysis, the data transferentity 11 initiates an operation of postponing the providing of chargingrelevant parameters associated with the transfer of the first dataobject, until receiving a predetermined message from the second entity3. It is noted that the criteria for initiating or not initiating thepostponement operation are the same as those described earlier, i.e.this may depend on the type of data in the first data object, theprovider of said data, the end-user or any combination thereof.

The start for performing the analysis in data transfer entity 11 can begiven in any desired or suitable way, e.g. by a constantly runningmonitoring procedure in the data transfer entity 11, or on the basis ofa start message sent by the first entity 2 (this is not shown in FIG. 4for simplicity). Such a start message could directly be sent from thefirst entity 2 to the data transfer entity 11, or via the terminaldevice 4. Similar to such a start message, first entity 2 can also bearranged to send a stop message for stopping the performing of theanalysis at data transfer entity 11. Instead of such dedicatedstart/stop messages, it is also possible to add a leading informationpacket to message 403 for starting the analysis operation and/or atrailing stop packet for stopping the analysis.

Then the data transfer entity 11 sends a message 405 to the first entity2, which message 405 contains coordination information, such as theacknowledgement that an analysis is being performed and that the datatransfer entity 11 will postpone forwarding the charging relevantparameters related to the transfer of the first object until receivingan appropriate triggering message. Preferably, message 405 also containsthe address of data transfer entity 11, which address may be passed ontothe second entity 3 in message 406.

In the example of FIG. 4 it is assumed that the user of terminal device4 sends a request message 407 to second entity 3, for requesting thesecond data object. In response thereto, the second entity 3 sends thepredetermined triggering message 408 (which corresponds to message 31 inFIG. 1) to the data transfer entity 11, such that the data transferentity may forward the charging relevant parameters associated with thetransfer of the first data object to charging entity 5 in message 409.It is noted that messages 407 to 412 fully correspond to messages 309 to314, respectively, described in connection with FIG. 3, such that afurther description of these messages and the associated controlprocedures and the alternatives at respective entities is not necessary.

Now, with respect to FIGS. 5 to 7 examples of signalling that correspondto the concept described in connection with FIG. 2 shall be described.

In the example of FIG. 5, the messages 501 and 502 and associatedcontrol operations in entities 2, 3 and 6 are identical to thosedescribed in connection with messages 301, 302 or 401, 402 in FIGS. 3and 4, such that a renewed description is not necessary.

With message 503, the first entity 2 sends information to terminaldevice 4, said information indicating that the charging and billingoperation on the basis of the transfer related parameters associatedwith the first data object is to be postponed until a predeterminedtriggering message is issued by the second entity 3. The controlprocedures leading to message 503, and message 503 itself correspond tothe control procedures leading up to message 303 and message 303 itselfas described in connection with FIG. 3, such that a renewed descriptionis not necessary here.

In response to receiving message 503, the terminal device sends acontrol message 504 to data transfer entity 11, similar to what wasdescribed in connection with message 304 in FIG. 3, such that a reneweddescription is not necessary. Consequently, the response message 505fully corresponds to message 305 of FIG. 3. The response on the part ofthe terminal device 4 is message 506, which corresponds to message 306of FIG. 3, just as message 507 corresponds to message 307 of FIG. 3.

However, in departure from the example of FIG. 3, the control operationshown in FIG. 5 has the message 508, with which the data transfer entity11 sends a control message to charging entity 5, to postpone theprocessing of charging relevant parameters related to the transfer ofthe first data object until receiving a predetermined triggering messagefrom second entity 3. Control message 508 can be a request message or acommand message.

Due to the fact that the charging operation is postponed at the chargingentity 5, the data transfer entity 11 can be operated to forward thecharging related parameters to the charging entity 5 as in aconventional data transfer entity. However, it is also possible toadditionally implement a postponement at the data transfer entity 11,and to have both the data transfer entity 11 and the charging entity 5wait for a triggering message from the second entity 3. This is,however, not shown in FIG. 5.

It may be noted that one benefit of sending the postponement controlmessage 508 to charging entity 5 at this stage is that a prepaid accountcan be checked to see whether the end-user to which the first dataobject is to be sent has enough credit for the transfer relatedcharging, e.g. for the volume if charging is based on volume. As aconsequence, as an additional option, charging entity 5 can be arrangedto perform such a check and return a corresponding acknowledgement tothe data transfer entity 11 (not shown in FIG. 5).

Returning to FIG. 5, in summary the operation is such that the controlmessage 508 is sent from data transfer entity 11 to charging entity 5,and prior to sending control message 508, a request message 504 is sentfrom terminal device 4 to data transfer entity 11 for requesting thedata transfer entity 11 to send the control message 508 to chargingentity 5.

In the example of FIG. 5, the first entity 2 sends the first data objectin a message 513 to terminal device 4. It is assumed that eventually theuser of terminal 4 sends a request 509 for the second data object, inresponse to which the second entity 3 sends a predetermined message 510that corresponds to the predetermined message 32 shown in FIG. 2.Namely, this message 510 serves to trigger the further processing of thetransfer related parameters associated with the transfer of the firstdata object, said transfer related parameters having been forwarded fromthe data transfer entity 11 to the charging entity 5 (not shown in FIG.5). Message 510 will preferably be also contain further information,such as information on the second data object that is relevant forcharging and billing.

It is in principle possible that the second entity 3 immediately sendsthe second data object to the requesting terminal device 4 uponreceiving the request 509, but in the example of FIG. 5 an additionalprocedure is implemented, according to which the charging entity 5 firstanalyses the information received in message 510 and decides whether toallow a sending of the second data object or not. This is similar towhat is described in connection with messages 312, 313 in FIG. 3, suchthat a renewed description is not necessary. If the charging entity 5allows the providing of the second data object, see message 511, thenthe second entity 3 provides the second data object in message 512.

FIG. 6 shows another embodiment of the present invention. The messages601, 602 and the corresponding control operations in entities 2, 3 and 6are identical to those described in connection with messages 301, 302with respect to FIG. 3, such that a renewed description is notnecessary.

Similar to message 508 described in connection with FIG. 5, in theexample of FIG. 6 a control message 607 is sent to the charging entityfor postponing the processing of the one or more charging relevantparameters related to the transfer of the first data object untilreceiving a predetermined message from the second entity 3. However, incontrast to FIG. 5, this control message 607 is not provided by the datatransfer entity 11, but much rather is sent by the first entity 2. Inorder to do this, an address acquisition procedure is conducted forproviding address information identifying the charging entity 5 toentity 2. This comprises sending an address information request message604 to the data transfer entity 11. Preferably, this is done via theterminal device 4 with a message 603. If the messaging is done viaterminal device 4, then data transfer entity responds with a returnmessage 605, containing the desired address information, which is thenforwarded to the first entity 2 in a message 606. The information isalso provided to the second entity 3 in message 613.

Optionally, messages 603 to 606 and the corresponding control procedurecan be similar to that of messages 503 to 506, respectively, describedin connection with FIG. 5. In other words, the control message 604 canalso contain a request for asking the data transfer entity 11 to decidewhether or not the charging on the basis of charging related parametersassociated with the transfer of the first data object should bepostponed. In this case, message 605 contains the grant or refusal ofsaid request.

Subsequent to sending control message 607, the first entity 2 sends thefirst data object in a message 608 to the terminal device 4. In FIG. 6it is assumed that eventually the user of terminal device 4 requests thesecond data object with a message 609. It is noted that the messages andaccompanying operation for messages 609 to 612 are identical to what hasbeen described in connection with messages 509 to 512 respectively, inFIG. 5, such that a renewed description is not necessary.

FIG. 7 shows a further embodiment, in which the charging entity 5receives a control message 705 for postponing the processing of chargerelated parameter values associated with the transfer of the first dataobject. Similar to the example of FIG. 6, the control message 705 issent by first entity 2 to charging entity 5. However, in contrast to theexample of FIG. 6, the request for addressing information on chargingentity 5 is sent directly from the first entity 2 to the data transferentity 11 in a message 703, to which the data transfer entity 11responds with message 704. It is noted that there may be a messageinterchange prior to message 703 between the first entity 2 and theterminal device 4, in order to obtain addressing information relating tothe data transfer entity 11 (this procedure not being shown in FIG. 7).It is noted that the remaining signalling and control procedurescorrespond to those of FIG. 6, more precisely message 706 corresponds tomessage 613, and messages 707 to 711 correspond to messages 608 to 612,respectively. Consequently, a renewed description is not necessary.

Optionally, messages 703, 704 and the corresponding control procedurecan be similar to that of messages 503 to 506, respectively, describedin connection with FIG. 5. In other words, the control message 703 canalso contain a request for asking the data transfer entity 11 to decidewhether or not the charging on the basis of charging related parametersassociated with the transfer of the first data object should bepostponed. In this case, message 704 contains the grant or refusal ofsaid request.

It is noted that the present invention not only relates to methods forcontrolling the overall communication system described in connectionwith FIGS. 1 and 2, but also to methods of controlling the individualentities in accordance with the above described concepts, and also theinvention relates to the entities themselves as embodied to operate inaccordance with such control procedures. In this case the entities arepreferably embodied as operating on a given server of the communicationsystem.

More specifically, the invention thereby also relates to a method ofcontrolling a server that acts as the second entity 3, where the serveris controlled to output the predetermined message 31 to the datatransfer entity 11 subsequent to receiving a request for the second dataobject from the terminal device 4, to thereby trigger the data transferentity 11 to provide the recorded charging relevant parameters to thecharging entity 5.

Furthermore, the invention relates to a control method and serverarranged to act as the data transfer entity 11, where the server iscontrolled so as to make the providing of one or more charging relevantparameters related to the transfer of the first data object dependent onthe receipt of the predetermined triggering message from the secondentity 3.

Furthermore, the invention relates to a server acting as said chargingentity 5, where the server is controlled so as to make the processing ofone or more charging relevant parameters that were received from thedata transfer entity 11 and relate to the transfer of the first dataobject, dependent on the receipt of the predetermined triggering messagefrom the second entity.

Furthermore, the invention also relates to a method of controlling theterminal device 4 and to an appropriately arranged terminal device 4, inwhich the terminal device sends a predetermined control message to thedata transfer entity 11, where the control message contains controlinformation for controlling the data transfer entity 11 to postpone theproviding of one or more charging relevant parameters related to thetransfer of the first data object until the data transfer entityreceives the predetermined triggering message from the second entity 3.

It is furthermore noted that the above-described control methods can beembodied in the form of computer software, and can consequently also beembodied in the form of data storage elements or data carriers holdingsuch computer software.

Although the present invention has been described on the basis ofpreferred detailed embodiments, these detailed embodiments only serve toprovide a more comprehensive understanding and are not intended to belimiting. Reference numerals in the claims serve to make the claimseasier to read, but are not intended to be limiting.

1. A method of controlling an operation of a communication system, saidsystem comprising: a first entity for sending a first data object to aterminal device, a second entity for sending a second data object tosaid terminal device, said second data object having a predeterminedassociation with said first data object, a data transfer entity fortransferring data to said terminal device and recording one or morecharging relevant parameters associated with the transfer of data tosaid terminal device, said data transfer entity being adapted totransfer said first data object to said terminal device, and said datatransfer entity being part of a communication network, a charging entityfor collecting and processing charging information related to theproviding of communication services by said communication network, saiddata transfer entity being adapted for providing recorded chargingrelevant parameters to said charging entity, said method comprising:controlling said first entity to send said first data object to saidterminal device, controlling said data transfer entity to record one ormore charging relevant parameters related to the transfer of said firstdata object to said terminal device, controlling said second entity tooutput a predetermined message to said data transfer entity subsequentto receiving a request for sending said second data object to saidterminal device, and controlling said data transfer entity to make theproviding of said one or more charging relevant parameters related tothe transfer of said first data object dependent on the receipt of saidpredetermined message.
 2. The method of claim 1, further comprisingsending a predetermined control message to said data transfer entityprior to controlling said first entity to send said first data object tosaid terminal device, said control message containing controlinformation for postponing the providing of said one or more chargingrelevant parameters until the receipt of said predetermined message. 3.The method of claim 2, wherein said control message is sent from saidterminal device to said data transfer entity.
 4. The method of claim 2,wherein said control message is a request message or a command message.5. The method of claim 1, further comprising controlling said datatransfer entity to perform an analysis of said first data object duringits transfer and, depending on a result of said analysis, to initiate anoperation of postponing the providing of said one or more chargingrelevant parameters until the receipt of said predetermined message. 6.A method of controlling an operation of a communication system, whereinsaid communication system comprises: a first entity for sending a firstdata object to a terminal device, a second entity for sending a seconddata object to said terminal device, said second data object having apredetermined association with said first data object, a data transferentity for transferring data to said terminal device and recording oneor more charging relevant parameters associated with the transfer ofdata to said terminal device, said data transfer entity being adapted totransfer said first data object to said terminal device, and said datatransfer entity being part of a communication network, a charging entityfor collecting and processing charging information related to theproviding of communication services by said communication network, saiddata transfer entity being adapted for providing recorded chargingrelevant parameters to said charging entity, said method comprising:controlling said first entity to send said first data object to saidterminal device, controlling said data transfer entity to record one ormore charging relevant parameters related to the transfer of said firstdata object to said terminal device, controlling said second entity tooutput a predetermined message to said charging entity subsequent toreceiving a request for sending said second data object to said terminaldevice, and controlling said charging entity to make the processing ofone or more charging relevant parameters related to the transfer of saidfirst data object dependent on the receipt of said predeterminedmessage.
 7. The method of claim 6, further comprising sending apredetermined control message to said charging entity prior tocontrolling said first entity to send said first data object to saidterminal device, said control message containing control information forpostponing the processing of said one or more charging relevantparameters until the receipt of said predetermined message.
 8. Themethod of claim 6, wherein said control message is a request message ora command message.
 9. The method of claim 7, wherein said controlmessage is sent from said data transfer entity to said charging entity.10. The method of claim 9, wherein prior to sending said control messagefrom said data transfer entity to said charging entity, a requestmessage is sent from said terminal device to said data transfer entityfor requesting said data transfer entity to send said control message.11. The method of claim 7, wherein said control message is sent to saidcharging entity from a control message source, said control messagesource being said first or said second entity.
 12. The method of claim11, wherein prior to sending said control message from said controlmessage source to said charging entity, an address acquisition procedurefor providing address information on the charging entity to said controlmessage source is conducted, said address acquisition procedurecomprising sending an address information request message to said datatransfer entity.
 13. The method of claim 12, wherein said addressinformation request message is sent directly from said control messagesource to said data transfer entity.
 14. The method of claim 12, whereinsaid address information request message is sent from said controlmessage source to said data transfer entity via said terminal device.15. The method of claim 6, wherein at least one of said at one or morecharging relevant parameters related to the transfer of said first dataobject is communicated from said first entity to said data transferentity.
 16. The method of claim 6, wherein at least one of said at oneor more charging relevant parameters related to the transfer of saidfirst data object is measured by said data transfer entity during thetransfer of said first data object.
 17. The method of claim 6, furthercomprising, subsequent to said second entity having received saidrequest for sending said second data object, controlling said secondentity to send an information message to said charging entity, saidinformation message comprising information associated with said seconddata object, and controlling said second entity to make the sending ofsaid second data object dependent on receiving an enable message fromsaid charging entity, and controlling said charging entity to conduct anenable message output procedure in response to receiving saidinformation message, comprising a decision step of whether or not tooutput said enable message that depends on the information contained insaid information message.
 18. The method of claim 6, further comprising:controlling said second entity to delete said second data object and tosend a notification message that informs of said deleting to one or bothof said data transfer entity and said charging entity if no request forsending said second data object to said terminal device is receivedwithin a predetermined time period since storing said second data objectat said second entity, and controlling one or both of said data transferentity and said charging entity to delete said one or more chargingrelevant parameters related to the transfer of said first data object inresponse to receiving said notification message.
 19. The method of claim6, wherein said first data object comprises data to be accessed by auser of said terminal device, and said second data object comprises datafor enabling access to the data of said first data object.
 20. Themethod of claim 6, wherein said request for sending said second dataobject to said terminal device is output by said terminal device.
 21. Amethod of controlling a server in a communication system, wherein saidcommunication system comprises: a first entity for sending a first dataobject to a terminal device, a second entity for sending a second dataobject to said terminal device, said second data object having apredetermined association with said first data object, a data transferentity for transferring data to said terminal device and recording oneor more charging relevant parameters associated with the transfer ofdata to said terminal device, said data transfer entity being adapted totransfer said first data object to said terminal device, and said datatransfer entity being part of a communication network, a charging entityfor collecting and processing charging information related to theproviding of communication services by said communication network, saiddata transfer entity being adapted for providing recorded chargingrelevant parameters to said charging entity, said server comprising saidsecond entity and said method comprising: controlling said second entityto output a predetermined message to said data transfer entitysubsequent to receiving a request for sending said second data object tosaid terminal device, for triggering said data transfer entity toprovide recorded charging relevant parameters associated with thetransfer of said first data object to said charging entity.
 22. Themethod of claim 21, further comprising, subsequent to said second entityhaving received said request for sending said second data object,controlling said second entity to send an information message to saidcharging entity, said information message comprising informationassociated with said second data object, and controlling said secondentity to make the sending of said second data object dependent onreceiving an enable message from said charging entity.
 23. The method ofclaim 21, further comprising controlling said second entity to deletesaid second data object and to send a notification message that informsof said deleting to one or both of said data transfer entity and saidcharging entity if no request for sending said second data object tosaid terminal device is received within a predetermined time periodsince storing said second data object at said second entity. 24-25.(canceled)
 26. A server coupled to a communication system, wherein saidcommunication system comprises: a first entity for sending a first dataobject to a terminal device, a second entity for sending a second dataobject to said terminal device, said second data object having apredetermined association with said first data object, a data transferentity for transferring data to said terminal device and recording oneor more charging relevant parameters associated with the transfer ofdata to said terminal device, said data transfer entity being adapted totransfer said first data object to said terminal device, and said datatransfer entity being part of a communication network, a charging entityfor collecting and processing charging information related to theproviding of communication services by said communication network, saiddata transfer entity being adapted for providing recorded chargingrelevant parameters to said charging entity, said server comprising:said second entity and said server being adapted to conduct a controlprocedure for controlling said second entity to output a predeterminedmessage to said data-transfer entity subsequent to receiving a requestfor sending said second data object to said terminal device, fortriggering said data transfer entity to provide recorded chargingrelevant parameters associated with the transfer of said first dataobject to said charging entity.
 27. The server of claim 26, wherein saidcontrol procedure is arranged for, subsequent to said second entityhaving received said request for sending said second data object,controlling said second entity to send an information message to saidcharging entity, said information message comprising informationassociated with said second data object, and controlling said secondentity to make the sending of said second data object dependent onreceiving an enable message from said charging entity.
 28. The server ofclaim 26, wherein said control procedure is arranged for controllingsaid second entity to delete said second data object and to send anotification message that informs of said deleting to one or both ofsaid data transfer entity and said charging entity if no request forsending said second data object to said terminal device is receivedwithin a predetermined time period since storing said second data objectat said second entity.
 29. A method of controlling a server in acommunication system, wherein said communication system comprisescomprising a first entity for sending a first data object to a terminaldevice, a second entity for sending a second data object to saidterminal device, said second data object having a predeterminedassociation with said first data object, a data transfer entity fortransferring data to said terminal device and recording one or morecharging relevant parameters associated with the transfer of data tosaid terminal device, said data transfer entity being adapted arrangedto transfer said first data object to said terminal device, and saiddata transfer entity being part of a communication network, a chargingentity for collecting and processing charging information related to theproviding of communication services by said communication network, saiddata transfer entity being adapted for providing recorded chargingrelevant parameters to said charging entity, said server comprising saiddata transfer entity and said method comprising: controlling said datatransfer entity to make the providing of said one or more chargingrelevant parameters related to the transfer of said first data objectdependent on the receipt of a predetermined message from said secondentity.
 30. The method of claim 29, further comprising controlling saiddata transfer entity to postpone the providing of said one or morecharging relevant parameters related to the transfer of said first dataobject in response to receiving a message containing a request orcommand for postponing the providing of said one or more chargingrelevant parameters until the receipt of said predetermined message. 31.The method of claim 29, further comprising controlling said datatransfer entity to perform an analysis of said first data object duringits transfer and, depending on a result of said analysis, to initiate anoperation of postponing the providing of said one or more chargingrelevant parameters until the receipt of said predetermined message. 32.The method of claim 29, wherein said data transfer entity receives atleast one of said one or more charging relevant parameters related tothe transfer of said first data object from said first entity.
 33. Themethod of claim 29, wherein at least one of said at one or more chargingrelevant parameters related to the transfer of said first data object ismeasured by said data transfer entity during the transfer of said firstdata object. 34-35. (canceled)
 36. A server coupled to a communicationsystem, wherein said communication system comprises: a first entity forsending a first data object to a terminal device, a second entity forsending a second data object to said terminal device, said second dataobject having a predetermined association with said first data object, adata transfer entity for transferring data to said terminal device andrecording one or more charging relevant parameters associated with thetransfer of data to said terminal device, said data transfer entitybeing adapted to transfer said first data object to said terminaldevice, and said data transfer entity being part of a communicationnetwork, a charging entity for collecting and processing charginginformation related to the providing of communication services by saidcommunication network, said data transfer entity being adapted forproviding recorded charging relevant parameters to said charging entity,said server comprising: said data transfer entity and said server beingadapted to conduct a control procedure for controlling said datatransfer entity to make the providing of said one or more chargingrelevant parameters related to the transfer of said first data objectdependent on the receipt of a predetermined message from said secondentity.
 37. The server of claim 36, wherein said control procedure isarranged for controlling said data transfer entity to postpone theproviding of said one or more charging relevant parameters related tothe transfer of said first data object in response to receiving amessage containing a request or command for postponing the providing ofsaid one or more charging relevant parameters until the receipt of saidpredetermined message.
 38. The server of claim 36, wherein said controlprocedure is arranged for controlling said data transfer entity toperform an analysis of said first data object during its transfer and,depending on a result of said analysis, to initiate an operation ofpostponing the providing of said one or more charging relevantparameters until the receipt of said predetermined message.
 39. Theserver of claim 35, wherein said control procedure is arranged forletting said data transfer entity receive at least one of said one ormore charging relevant parameters related to the transfer of said firstdata object from said first entity.
 40. The server of claim 36, whereinsaid control procedure is arranged for controlling said data transferentity to measure at least one of said at one or more charging relevantparameters related to the transfer of said first data object during thetransfer of said first data object.
 41. A method of controlling a serverin a communication system, wherein said communication system comprises afirst entity for sending a first data object to a terminal device, asecond entity for sending a second data object to said terminal device,said second data object having a predetermined association with saidfirst data object, a data transfer entity for transferring data to saidterminal device and recording one or more charging relevant parametersassociated with the transfer of data to said terminal device, said datatransfer entity being adapted to transfer said first data object to saidterminal device, and said data transfer entity being part of acommunication network, a charging entity for collecting and processingcharging information related to the providing of communication servicesby said communication network, said data transfer entity being adaptedfor providing recorded charging relevant parameters to said chargingentity, said server comprising said charging entity and said methodcomprising: controlling said charging entity to make the processing ofone or more charging relevant parameters related to the transfer of saidfirst data object dependent on the receipt of a predetermined messagefrom said second entity.
 42. The method of claim 41, further comprisingcontrolling said charging entity to postpone the processing of said oneor more charging relevant parameters related to the transfer of saidfirst data object in response to receiving a message containing arequest or command for postponing the processing of said one or morecharging relevant parameters until the receipt of said predeterminedmessage. 43-44. (canceled)
 45. A server coupled to a communicationsystem, wherein said communication system comprises: a first entity forsending a first data object to a terminal device, a second entity forsending a second data object to said terminal device, said second dataobject having a predetermined association with said first data object, adata transfer entity for transferring data to said terminal device andrecording one or more charging relevant parameters associated with thetransfer of data to said terminal device, said data transfer entitybeing adapted to transfer said first data object to said terminaldevice, and said data transfer entity being part of a communicationnetwork, a charging entity for collecting and processing charginginformation related to the providing of communication services by saidcommunication network, said data transfer entity being adapted forproviding recorded charging relevant parameters to said charging entity,said server comprising: said charging entity and said server beingarranged to conduct a control procedure for controlling said chargingentity to make the processing of one or more charging relevantparameters related to the transfer of said first data object dependenton the receipt of a predetermined message from said second entity. 46.The server of claim 45, wherein said control procedure is arranged forcontrolling said charging entity to postpone the processing of said oneor more charging relevant parameters related to the transfer of saidfirst data object in response to receiving a message containing arequest or command for postponing the processing of said one or morecharging relevant parameters until the receipt of said predeterminedmessage.
 47. A method of controlling a terminal device in acommunication system, wherein said communication system comprises: afirst entity for sending a first data object to said terminal device, asecond entity for sending a second data object to said terminal device,said second data object having a predetermined association with saidfirst data object, a data transfer entity for transferring data to saidterminal device and recording one or more charging relevant parametersassociated with the transfer of data to said terminal device, said datatransfer entity being adapted to transfer said first data object to saidterminal device, and said data transfer entity being part of acommunication network, a charging entity for collecting and processingcharging information related to the providing of communication servicesby said communication network, said data transfer entity being adaptedfor providing recorded charging relevant parameters to said chargingentity, said method comprising: controlling said terminal device to senda predetermined control message to said data transfer entity, saidcontrol message containing control information for controlling said datatransfer entity to postpone the providing of one or more chargingrelevant parameters related to the transfer of said first data objectuntil said data transfer entity receives a predetermined message fromsaid second entity.
 48. The method of claim 47, further comprisingcontrolling said terminal device to send said predetermined controlmessage in response to receiving from said first or second entity arequest for sending said control message.
 49. The method of claim 47,further comprising controlling said terminal device to output to saidsecond entity a request for sending said second data object to saidterminal device. 50-51. (canceled)
 52. A terminal device in acommunication system, wherein said communication system comprises: afirst entity for sending a first data object to said terminal device, asecond entity for sending a second data object to said terminal device,said second data object having a predetermined association with saidfirst data object, a data transfer entity for transferring data to saidterminal device and recording one or more charging relevant parametersassociated with the transfer of data to said terminal device, said datatransfer entity being adapted to transfer said first data object to saidterminal device, and said data transfer entity being part of acommunication network, a charging entity for collecting and processingcharging information related to the providing of communication servicesby said communication network, said data transfer entity being adaptedfor providing recorded charging relevant parameters to said chargingentity, said terminal device being adapted to conduct a controlprocedure for controlling said terminal device to send a predeterminedcontrol message to said data transfer entity, said control messagecontaining control information for controlling said data transfer entityto postpone the providing of one or more charging relevant parametersrelated to the transfer of said first data object until said datatransfer entity receives a predetermined message from said secondentity.
 53. The terminal device of claim 52, wherein said terminaldevice is adapted to send said predetermined control message in responseto receiving from said first or second entity a request for sending saidcontrol message.
 54. The terminal device of claim 52, being adapted tobe controllable to output to said second entity a request for sendingsaid second data object to said terminal device.